Method for accelerating the activation of a mbms service

ABSTRACT

The invention relates to a method for accelerating the activation of a MBMS service distributed by a service provider to a plurality of user equipments UEs in the form of MBMS data packets, MBMS data packet, comprising each, compressed header information and a payload, characterized by:—creating a specific MBMS service data flow containing only header information,—transmitting said specific MBMS service data flow to the UE separately from said MBMS data packets.

TECHNICAL DOMAIN

The invention pertains to telecommunication field and concerns a method for accelerating the activation of a Multimedia Broadcast Multicast Service (MBMS) distributed by a service provider to a plurality of user equipments (UEs) in the form of MBMS data packets, comprising each, compressed header information and a payload.

The invention concerns also a User Equipment adapted for receiving such MBMS services and a Server adapted for distributing such MBMS services.

STATE OF PRIOR ART

Multimedia Broadcast Multicast Service (MBMS) is a broadcasting service that can be offered via existing GSM and UMTS cellular networks. The infrastructure offers an option to use an uplink channel for interaction between the service and the user, which is not provided in usual broadcast networks, as for example conventional digital television which is only a one-way (unidirectional) system. MBMS uses multicast distribution in the core network instead of point-to-point links for each end device.

It is expected that MBMS will be rolled out in cellular networks and gives the opportunity to broadcast TV, film, information and other media in these networks. MBMS has the major benefits that the network infrastructure is already there for mobile network operators and the deployment can be cost effective compared with building a new network for the services. The broadcast capability enables to reach unlimited number of users with constant network load. Further, it also enables the possibility to broadcast information simultaneously to many cellular subscribers for example emergency alerts.

The MBMS feature is split into the MBMS Bearer Service and the MBMS User Service. The MBMS Bearer Service includes a Multicast- and a Broadcast Mode. The MBMS Bearer Service uses IP Multicast addresses for the IP flows. The advantage of the MBMS Bearer Service compared to legacy UMTS bearer services (interactive, streaming, etc) is, that the transmission resources in the core- and radio network are shared. One MBMS packet flow is replicated by GGSN, SGSN and RNCs. MBMS may use an advanced counting scheme to decide, whether or not zero, one or more dedicated (i.e. unicast) radio channels lead to a more efficient system usage than one common (i.e. broadcast) radio channel.

The MBMS User Service is basically the MBMS Service Layer and offers a Streaming and a Download Delivery Method. The Streaming Delivery method can be used for continuous transmissions like Mobile TV services. The Download Method is intended for “Download and Play” services.

One problem in the reception of MBMS service when header compression techniques are used for the MBMS data is generated by the delay introduced by header compression when a user of a MBMS reception device activates a service.

As a matter of fact, when a user initiates reception of an MBMS transmission on its MBMS reception device, e.g. a TV channel, there is some delay before the service becomes available to the user, e.g. before the service is displayed on the screen, due to initial buffering in the codec layers.

In addition, because of the header compression applied to the headers of the MBMS data packets (e.g. RTP/IP headers), there is an additional delay until the headers can be successfully decompressed and the MBMS data can be provided to the codec layers. Successful decompression of the headers for a flow of MBMS data is only possible after one or more date packets containing full header information is received, while such packets may be transmitted only infrequently, e.g. every 5 or 10 s.

The delay introduced by header compression is the time until one or more MBMS data packets are transmitted with full header information. Such transmission typically occurs in a periodic manner, or when there is a change, which is a rather infrequent event. While it is possible for the header compression entity to increase the frequency of transmission, this decreases the gain of header compression.

An object of the invention is to eliminate this delay without decreasing the gain of header compression.

PRESENTATION OF THE INVENTION

The object of the invention is achieved by a method for accelerating the activation of a MBMS service distributed by a service provider to a plurality of user equipments UEs in the form of MBMS data packets, comprising each, compressed header information and a payload representing the service such as video and/or audio data streams.

The method according to the invention comprises the following steps:

-   creating a specific MBMS service data flow containing only header     information, -   transmitting said specific MBMS service data flow to the UE     separately from said MBMS data packets.

In a first embodiment of the method according to the invention, said specific MBMS service data flow is transmitted to the UEs over a MBMS Traffic Channel (MTCH).

In a second embodiment of the method according to the invention, said specific MBMS service data flow is transmitted to the UEs over a MBMS Control Channel (MCCH).

In both embodiments, The UEs receiving the MBMS services are configured to continuously read and maintain exhaustive header information for a set of MBMS services by receiving MCCH or the specific MBMS services carrying only header information.

Thanks to this feature, there is no delay due to header compression when the user wishes to receive such a service.

The identity of the MBMS service containing the only header information is indicated either:

-   in the service announcement for the MBMS service containing the     payload. This information is provided by the BMSC, in case of MBMS     UTRAN/GERAN architecture, provided by the MBMS Gateway in case of     E-UTRAN) -   in the MCCH control information related to the MBMS service     containing the real data. This information is provided by the     RNC/BSC/MCE or eNB in case of MBMS UTRAN/GERAN/E-UTRAN architecture.

Preferably, said specific MBMS service data flow is transmitted to the UEs with scheduling information indicating the occurrence date of the next transmissions of a service on MTCH in order to stop reception in-between.

In an alternative variant, said specific MBMS service data flow is transmitted to the UEs with reference periods of the MCCH for notifying the change of the information related to a specific MBMS service data flow compared with the previous reference period.

It is then possible to make the power consumption really low while maintaining up to date information for several MBMS services.

It is to be noted that, the continuous reception of the MCCH or the specific MBMS services carrying only header information causes additional power consumption for the UEs. However, it is possible to arrange the transmission of the header information in a way that takes advantage of all the existing power saving techniques applied to reception of an MBMS Traffic Channel or of the MBMS Control Channel such as:

-   scheduling information (e.g. called MSCH, Scheduling Block, dynamic     scheduling information or whatsoever) that indicates when the next     transmissions of a service on MTCH may occur so the receiving device     may stop reception in-between, -   reference periods (called “Modification Periods”) of the MCCH with     notifications when the information related to a MBMS is changed     compared with the previous reference period, using either or both -   an MBMS Indicator Channel (MICH) which the UE can monitor instead of     MCCH; -   an arrangement of MBMS control information on MCCH where control     information (e.g. MBMS MODIFIED SERVICES INFORMATION message) is     transmitted as the start of each reference period and includes the     list of MBMS services for which modified information will be     transmitted.

Furthermore, the header information may change after it was last transmitted on MCCH or MTCH separately from the MBMS data. In this case, when it starts reception of an MBMS service, the UEs may be using outdated header information. In the worst case, this may confuse the header decompression entity in the MBMS reception device, cause incorrect data to be transmitted to the codec layers, and possibly lead to e.g. confused video stream or unpleasant sounds to be played.

In order to avoid such consequences, a piece of information is included together with MBMS data packets on MTGH which allows the MBMS reception device to know that a change occurred since it was last transmitted in one of the two ways mentioned above. This piece of information can be.

-   one single-bit indicated the MBMS device should not rely on the     previously stored header information acquired from the separate MTCH     or from MCCH -   a value tag increased by one at each change, included with the MBMS     data information and with the separate header information for this     MBMS service, so that the UEs may check if it has an up to date     value and discard the data if not.

This single-bit or value tag may be transmitted using certain bits in the MAC, or the RLC of the PDCP header of the MBMS data packets, or a special field if transmitted on MCCH either:

-   with each MBMS data packet transmitted on the MTCH carrying the data     with compressed headers, or, -   with each MBMS packet containing header information on the     associated MTCH, or header information on MCCH.

The User Equipment intended to receive the MBMS service comprises means for receiving specific MBMS service data flow containing only header information transmitted separately from said MBMS data packets.

Said UEs are configured for acquiring and maintaining the header information for several MBMS services while not receiving said MBMS services.

The server distributing said MBMS services comprises:

-   means for creating a specific MBMS service data flow containing only     header information, -   means for transmitting said specific MBMS service data flow to the     UEs separately from said MBMS data packets.

BRIEF DESCRIPTION OF THE FIGURE

Other features and advantages of the invention will appear from the following description taken as a non limiting example with reference to the following drawings in witch;

FIG. 1 illustrates sequential operations of an MBMS reception device of the prior art without header compression,

FIG. 2 illustrates the delay between the first and the last step of sequential operations of FIG. 1,

FIG. 3 illustrates sequential operations of an MBMS reception device of the prior art with header compression,

FIG. 4 illustrates the delay between the first and the last step of sequential operations of FIG. 3,

FIG. 5 illustrates an example of existing power saving techniques for acquisition of MCCH information,

FIG. 6 illustrates sequential operations of an MBMS reception device according to a first embodiment of the invention using an example of power saving techniques for acquisition of MCCH information,

FIG. 7 illustrates the delay between the first and the last step of sequential operations of FIG. 6,

FIG. 8 illustrates sequential operations of an MBMS reception device according to a second embodiment of the invention,

FIG. 9 the delay between the first and the last step of sequential operations of FIG. 8.

FIG. 10 is a particular embodiment of the invention.

DESCRIPTION OF A DETAILED EMBODIMENT OF THE INVENTION

FIG. 1 illustrates the fully sequential operation of a User Equipment device (or the operation of an User Equipment device upon startup) for receiving a MBMS video program without header compression.

At step 2, the UE selects the broadcasting channel of said MBMS video program. At step 4, the UE acquires the configuration for receiving said MBMS video program. Step 6 The UE device configures the reception module for receiving said video program. At step 8, the video program is received and buffered, and displayed to step 10.

The delay between the first step 2 and the last step 10 is illustrated by FIG. 2.

Steps 2 and 4 respectively use ½ modification period and the delay for receiving control information transmitted as the start of each reference periods (called “Modification Periods”) of a MCCH channel (for MBMS MODIFIED channel) indicating when the information related to a MBMS is changed compared with the previous reference period.

The duration of step 6 is between 50 ms and 100 ms.

The buffering step 8 necessitates 5 ms to 10 ms.

Referring now to FIG. 3, the fully sequential operation of a User Equipment device (or the operation of an User Equipment device upon startup) for receiving a MBMS video program with header compression further comprises step 12 consisting in the initiation of the MBMS video program decompression. The delay between the first step 2 and step 10, before displaying the video program, is identical to the one of FIG. 2. However, 1 second to 5 seconds are added to the delay at the reception stage due to the decompression step 12 of header information before the buffering step 8.

It appears that when header compression is used, because header information is only transmitted infrequently, e.g. every 1 s to 5 s, there is an additional delay in the total time.

However, the method according to the invention implements the already existing techniques, in order to acquire and maintain configuration for several MBMS channels simultaneously with the reception of a MBMS channel, or even while not actually receiving any of them. This is possible thanks to the arrangement of transmission as illustrated in FIG. 5 where on MCCH, the “change information” indicates whether any change in the configuration information occurred since the last modification period. Once the UE reception device has read the “change information”, if it indicates a change, it goes on receiving MCCH; otherwise, it stops reception of MCCH until the next modification period.

In this case, two processes A and B are executed in parallel as represented in FIG. 6.

Process A comprises the following steps:

-   powering on of the Ue reception device (step 14), -   acquiring the configuration for the MBMS services (step 4), -   monitoring the configuration for the MBMS services (step 16).

Process B comprises the following steps:

-   requesting by the user a particular MBMS service (e. g. a specific     MBMS video program) (step 2), -   configuring the reception module of the UE for said particular MBMS     service (step 6), -   initiation of header decompression (step 12), -   buffering received MBMS services (step 8). -   displaying the buffered MBMS services (step 10),

The total delay for these two processes until the displaying step of the requested MBMS service is illustrated by FIG. 7 where it can be seen that, before the MBMS date reception, the configuration of the UE take 50 milliseconds to 100 milliseconds, and at the MBMS data reception step, the initialisation of the header context information and the buffering respectively take 1 ms to 5 ms and 5 ms to 10 ms.

FIG. 8 illustrates an embodiment of the invention according to which the header information is included in the MCCH, together with configuration information, so that the MBMS reception device can acquire this information for all MBMS services

In this case, two processes C and D are executed in parallel as represented in FIG. 8.

Process C comprises the following steps:

-   powering on of the Ue reception device (step 20), -   acquiring the MCCH containing the configuration for all the MBMS     services and the header information for said service (step 22), -   monitoring the configuration for the MBMS services (step 16) as in     process A.

Process D comprises the following steps:

-   requesting by the user a particular MBMS service (e. g. a specific     MBMS video program) (step 2) as in process B, -   configuring the reception module of the UE for said particular MBMS     service (step 6) in process B, -   buffering received MBMS services (step 8) in process B, -   displaying the buffered MBMS services (step 10) in process B.

The total delay for these two processes until the displaying step of the requested MBMS service is illustrated by FIG. 9 where it can be seen that, before the MBMS data reception, the configuration of the UE take 50 ms to 100 ms, and at the MBMS data reception step, the buffering step takes 5 ms to 10 ms.

FIG. 10 illustrates an embodiment of the invention according to which the header information is transmitted over a Transport Channel as a separate MBMS services, which is time multiplexed with the other MBMS services. The scheduling information (also called “MSCH”) is included, that indicates where header information are transmitted for a particular MBMS service. 

1. A method for accelerating the activation of a MBMS service distributed by a service provider to a plurality of user equipments UEs in the form of MBMS data packets, MBMS data packet, comprising each, compressed header information and a payload, the method comprising: creating a specific MBMS service data flow containing only header information, transmitting said specific MBMS service data flow to the UE separately from said MBMS data packets.
 2. The method according to claim 1 wherein said specific MBMS service data flow is transmitted to the UEs over a MBMS Traffic Channel (MTCH).
 3. The method according to claim 1 wherein said specific MBMS service data flow is transmitted to the UEs over a MBMS Control Channel (MCCH).
 4. The method according to claim 2 wherein said UEs are configured to continuously read said MBMS Traffic Channel (MTCH) in order to maintain exhaustive header information for a set of MBMS services.
 5. The method according to claim 1 wherein said specific MBMS service data flow is transmitted to the UEs with scheduling information indicating the occurrence data of the next transmissions of a service on MTCH in order to stop reception in-between.
 6. The method according to claim 1 wherein said specific MBMS service data flow is transmitted to the UEs with reference periods of the MCCH for notifying the change of the information related to a specific MBMS service data flow compared with the previous reference period.
 7. The method according to claim 6 wherein the notification of the change of the information related to a specific MBMS service data flow is carried out by means of an MBMS indicator channel (MICH) monitored by UEs.
 8. The method according to claim 6 wherein the notification of the change of the information related to a specific MBMS service data flow is carried out by means of an arrangement of MBMS control information on MCCH where control information is transmitted as the start of each reference period and includes the list of MBMS services for which modified information will be transmitted.
 9. The method according to claim 1 wherein, said specific MBMS service data flow is identified by means of MCCH control information related to the MBMS service containing the payload.
 10. A User Equipment adapted for receiving MBMS service distributed by a service provider in the form of MBMS data packets comprising compressed header information and a payloads, said User Equipment comprising a reception unit that receives specific MBMS service data flow containing only header information transmitted separately from said MBMS data packets.
 11. The User Equipment according to claim 10 configured for acquiring and maintaining the header information for several MBMS services while not receiving said MBMS services.
 12. A server adapted for distributing MBMS services to a plurality of user equipments UEs in the form of MBMS data packets comprising compressed header information and a payloads, said server comprising: a creation unit that creates a specific MBMS service data flow containing only header information, a transmission unit that transmits said specific MBMS service data flow to the UEs separately from said MBMS data packets.
 13. The method according to claim 3 wherein said UEs are configured to continuously read said MBMS Control Channel (MCCH) in order to maintain exhaustive header information for a set of MBMS services. 